Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37cce39629042517fff33878c34a61e73f5b8ffc39d7809bf5e15f7983e456fa

Tx prefix hash: 79e5a160a9537bbb43c05816d4273e1ba87a80130a075241c0f33280777739c3
Tx public key: 2c75a963b13721dd07928c76c831c2cd2d0a7753ad8ff968d042d12ff9b4f10e
Timestamp: 1712188514 Timestamp [UCT]: 2024-04-03 23:55:14 Age [y:d:h:m:s]: 01:073:19:05:40
Block: 992768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313658 RingCT/type: yes/0
Extra: 012c75a963b13721dd07928c76c831c2cd2d0a7753ad8ff968d042d12ff9b4f10e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6307eddd35e8c2f034acc0eab9b5fa4d765ea45ac6c7272060b0b85916716006 0.600000000000 1453142 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": 992778, "vin": [ { "gen": { "height": 992768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6307eddd35e8c2f034acc0eab9b5fa4d765ea45ac6c7272060b0b85916716006" } } ], "extra": [ 1, 44, 117, 169, 99, 177, 55, 33, 221, 7, 146, 140, 118, 200, 49, 194, 205, 45, 10, 119, 83, 173, 143, 249, 104, 208, 66, 209, 47, 249, 180, 241, 14, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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