Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73c45129ec2e9f5967d5503dfc0b8c9dcc105942b4cba978e96b926dc039577e

Tx prefix hash: 800693f756785c61bc89fa07caf93c326b6f981494a00fb86a5b9360ff862273
Tx public key: 2b8ae1db3e6110b948f17f8197fa151abd99608e61a2738d7c216cd195dce5a1
Timestamp: 1717331083 Timestamp [UCT]: 2024-06-02 12:24:43 Age [y:d:h:m:s]: 01:161:15:01:03
Block: 1035440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374087 RingCT/type: yes/0
Extra: 012b8ae1db3e6110b948f17f8197fa151abd99608e61a2738d7c216cd195dce5a102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b5448b4d21177c718ae9461ad7cd90aebbaa4a00afe454524ee391d24b76e5 0.600000000000 1503961 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": 1035450, "vin": [ { "gen": { "height": 1035440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b5448b4d21177c718ae9461ad7cd90aebbaa4a00afe454524ee391d24b76e5" } } ], "extra": [ 1, 43, 138, 225, 219, 62, 97, 16, 185, 72, 241, 127, 129, 151, 250, 21, 26, 189, 153, 96, 142, 97, 162, 115, 141, 124, 33, 108, 209, 149, 220, 229, 161, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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