Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 172d1d81b6eae888788f4cef4724d2d9b854132cfcc7dbca6563e9f81d646494

Tx prefix hash: e6fd56628df8033f38d6ce2162165046a1d75196cf2487a90f8d1c583c672a60
Tx public key: 0c4d0faaa02d9655e7c052de85b88e47a53517592f94229cddc021969c9817f2
Timestamp: 1744790831 Timestamp [UCT]: 2025-04-16 08:07:11 Age [y:d:h:m:s]: 00:218:17:38:02
Block: 1262572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154049 RingCT/type: yes/0
Extra: 010c4d0faaa02d9655e7c052de85b88e47a53517592f94229cddc021969c9817f20211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 352edc3c0d5cca5cffae3befa9f2c3d013df7dd6063002ddbcc380a8b3d4493c 0.600000000000 1749753 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1262582, "vin": [ { "gen": { "height": 1262572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "352edc3c0d5cca5cffae3befa9f2c3d013df7dd6063002ddbcc380a8b3d4493c" } } ], "extra": [ 1, 12, 77, 15, 170, 160, 45, 150, 85, 231, 192, 82, 222, 133, 184, 142, 71, 165, 53, 23, 89, 47, 148, 34, 156, 221, 192, 33, 150, 156, 152, 23, 242, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8