Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3395612f6109b2f01c98931e7ba07975fe63a0f8c2dc0d65870a7bc70d12bf

Tx prefix hash: ed2a586406d849453e6bee4153147ef42a6f248283f1f7b1b0432ed6e6acd8ac
Tx public key: b8f92953ef2fa060c03ea93c9162ccd6eabea7a1108f77b78226c8476af1695b
Timestamp: 1747503719 Timestamp [UCT]: 2025-05-17 17:41:59 Age [y:d:h:m:s]: 00:187:14:03:06
Block: 1285041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131758 RingCT/type: yes/0
Extra: 01b8f92953ef2fa060c03ea93c9162ccd6eabea7a1108f77b78226c8476af1695b02110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bbdae530f45a633126f79f60e2f1243452d48401129c3e58390975a6dcb1481 0.600000000000 1772504 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": 1285051, "vin": [ { "gen": { "height": 1285041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bbdae530f45a633126f79f60e2f1243452d48401129c3e58390975a6dcb1481" } } ], "extra": [ 1, 184, 249, 41, 83, 239, 47, 160, 96, 192, 62, 169, 60, 145, 98, 204, 214, 234, 190, 167, 161, 16, 143, 119, 183, 130, 38, 200, 71, 106, 241, 105, 91, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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