Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ac14ce8659a63feac58ce8983b9e23c873b7f8f599bf62f65a43ebbbf223a9

Tx prefix hash: 1d5796d2c142aaa276f26066ba0e290ba129df9b4b8964d145cc06d1c08eeb1c
Tx public key: bf56a673a1d820396a035f81f625c1e97cd87cdaee2b9627147192f54f2eba69
Timestamp: 1745972979 Timestamp [UCT]: 2025-04-30 00:29:39 Age [y:d:h:m:s]: 00:006:19:56:18
Block: 1272374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4880 RingCT/type: yes/0
Extra: 01bf56a673a1d820396a035f81f625c1e97cd87cdaee2b9627147192f54f2eba690211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 102737d65df9e4291cf2c3012c3a5e459f1e9bcca440234aa9f8019a193cfc47 0.600000000000 1759649 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": 1272384, "vin": [ { "gen": { "height": 1272374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102737d65df9e4291cf2c3012c3a5e459f1e9bcca440234aa9f8019a193cfc47" } } ], "extra": [ 1, 191, 86, 166, 115, 161, 216, 32, 57, 106, 3, 95, 129, 246, 37, 193, 233, 124, 216, 124, 218, 238, 43, 150, 39, 20, 113, 146, 245, 79, 46, 186, 105, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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