Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a13735a9c17c08f85946bf0709fcaa0a43ce29e34f6dfe3fb1a3605dc1ec38

Tx prefix hash: ee4699f44f1d1de332909ab2f57c89775907e910a8baa5cdec89929e78af6608
Tx public key: 0152f1bade8a23220e991d8682aee74ff73a6cce06f4af99b3f8fdaa08b4263f
Timestamp: 1764832344 Timestamp [UCT]: 2025-12-04 07:12:24 Age [y:d:h:m:s]: 00:031:09:21:32
Block: 1426110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22488 RingCT/type: yes/0
Extra: 010152f1bade8a23220e991d8682aee74ff73a6cce06f4af99b3f8fdaa08b4263f02110000000bd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dafacf93eaff1e7b643d6f975132cee3cf86c7395c1b2dfcff8f33c160dc6603 0.600000000000 1914793 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": 1426120, "vin": [ { "gen": { "height": 1426110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dafacf93eaff1e7b643d6f975132cee3cf86c7395c1b2dfcff8f33c160dc6603" } } ], "extra": [ 1, 1, 82, 241, 186, 222, 138, 35, 34, 14, 153, 29, 134, 130, 174, 231, 79, 247, 58, 108, 206, 6, 244, 175, 153, 179, 248, 253, 170, 8, 180, 38, 63, 2, 17, 0, 0, 0, 11, 214, 225, 157, 124, 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