Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e460693faf785e66b19c9663f85489b6df0bee34a775281baf2fc33926eee734

Tx prefix hash: 02dd935b480d5274f6dfa2d48607207fe1a761e28b28395d25e0b9e68fdbbdce
Tx public key: 9c8941e83c579a967bdf4b3aa28627013fc3f011fe9c672953616a9b099dbca8
Timestamp: 1760029369 Timestamp [UCT]: 2025-10-09 17:02:49 Age [y:d:h:m:s]: 00:040:21:05:44
Block: 1386290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29281 RingCT/type: yes/0
Extra: 019c8941e83c579a967bdf4b3aa28627013fc3f011fe9c672953616a9b099dbca8021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa4a068a0f0b15be9036d935ea781175324b699e91a9f13d670c0c70e5c7adb 0.600000000000 1874455 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": 1386300, "vin": [ { "gen": { "height": 1386290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa4a068a0f0b15be9036d935ea781175324b699e91a9f13d670c0c70e5c7adb" } } ], "extra": [ 1, 156, 137, 65, 232, 60, 87, 154, 150, 123, 223, 75, 58, 162, 134, 39, 1, 63, 195, 240, 17, 254, 156, 103, 41, 83, 97, 106, 155, 9, 157, 188, 168, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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