Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd87e1e10522340350817bf6577c406abbfdbfa6582fafbbb9ea1aa68c2b4a3c

Tx prefix hash: 59fb91d44299fbcd592779e9b4e93e10bca643d8a6d44a70d1d57de5789e13f1
Tx public key: a4f73b72c1d5ea703870a6fa56a9a15e5a545ad259bb238a0d2f311b77db2d6e
Timestamp: 1765728633 Timestamp [UCT]: 2025-12-14 16:10:33 Age [y:d:h:m:s]: 00:006:20:53:17
Block: 1433525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4927 RingCT/type: yes/0
Extra: 01a4f73b72c1d5ea703870a6fa56a9a15e5a545ad259bb238a0d2f311b77db2d6e0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8cbe5c3130ff0fac21c307e81b83cae546f25184c59b0da4c65f6697008b947 0.600000000000 1922306 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": 1433535, "vin": [ { "gen": { "height": 1433525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8cbe5c3130ff0fac21c307e81b83cae546f25184c59b0da4c65f6697008b947" } } ], "extra": [ 1, 164, 247, 59, 114, 193, 213, 234, 112, 56, 112, 166, 250, 86, 169, 161, 94, 90, 84, 90, 210, 89, 187, 35, 138, 13, 47, 49, 27, 119, 219, 45, 110, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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