Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a84b8223fa2f455a992d5b38c8c62ba8ce9b1d0faf7bbce8380455f01b07b4

Tx prefix hash: 8c39bd81e353c1c6ab8ec9af3346e76c06299388082927fa249d0977cdf54a98
Tx public key: bfb529820cb8c283f6fda10ca148b90ffc94e662b5ddcd5c8e75d72115b5c6ab
Timestamp: 1750638341 Timestamp [UCT]: 2025-06-23 00:25:41 Age [y:d:h:m:s]: 00:151:11:31:54
Block: 1310780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106153 RingCT/type: yes/0
Extra: 01bfb529820cb8c283f6fda10ca148b90ffc94e662b5ddcd5c8e75d72115b5c6ab021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffb8a1aa96b72daf54c61d68462ceb47d554589f5c81270843467ad79eb14592 0.600000000000 1798403 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": 1310790, "vin": [ { "gen": { "height": 1310780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffb8a1aa96b72daf54c61d68462ceb47d554589f5c81270843467ad79eb14592" } } ], "extra": [ 1, 191, 181, 41, 130, 12, 184, 194, 131, 246, 253, 161, 12, 161, 72, 185, 15, 252, 148, 230, 98, 181, 221, 205, 92, 142, 117, 215, 33, 21, 181, 198, 171, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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