Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 719c1584320c4b7f7419d4f0360634fdcd391d636a2ff35bc2e3d417c7b460e7

Tx prefix hash: c608284701a97a64d508d83725b934d267af2ce59fc01b50c67c08fcc1619a7f
Tx public key: 7a1909a3d7a1b342f668917e39128f2ea981638b273622943da433c0a30ff3cb
Timestamp: 1752092413 Timestamp [UCT]: 2025-07-09 20:20:13 Age [y:d:h:m:s]: 00:140:11:34:44
Block: 1322165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98953 RingCT/type: yes/0
Extra: 017a1909a3d7a1b342f668917e39128f2ea981638b273622943da433c0a30ff3cb0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5a0c33db7fd3af195c0c3cebbaea86e3fb3768d17a200e5241002870dc829e2 0.600000000000 1809882 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": 1322175, "vin": [ { "gen": { "height": 1322165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5a0c33db7fd3af195c0c3cebbaea86e3fb3768d17a200e5241002870dc829e2" } } ], "extra": [ 1, 122, 25, 9, 163, 215, 161, 179, 66, 246, 104, 145, 126, 57, 18, 143, 46, 169, 129, 99, 139, 39, 54, 34, 148, 61, 164, 51, 192, 163, 15, 243, 203, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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