Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f8e2534d1b025b63c4027f5e10846b86668aefb7b72c421f472c21480dd358

Tx prefix hash: 47b256c0c8ee5452ea6f04dd745c08d792f3e3140c5f6c2c203541cb36dc13d2
Tx public key: bd829e456db19b262b7f8e630c753d470c3c890027873765cddf2c49d4737dfd
Timestamp: 1700432093 Timestamp [UCT]: 2023-11-19 22:14:53 Age [y:d:h:m:s]: 01:099:09:36:55
Block: 895324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332187 RingCT/type: yes/0
Extra: 01bd829e456db19b262b7f8e630c753d470c3c890027873765cddf2c49d4737dfd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.662857099000 dcy

stealth address amount amount idx
00: 323643469e9de3bc7017ed1d16515c3259710eae107b74f4675cab4c6f2f9fb7 0.662857099000 1351555 of 0

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": 895334, "vin": [ { "gen": { "height": 895324 } } ], "vout": [ { "amount": 662857099, "target": { "key": "323643469e9de3bc7017ed1d16515c3259710eae107b74f4675cab4c6f2f9fb7" } } ], "extra": [ 1, 189, 130, 158, 69, 109, 177, 155, 38, 43, 127, 142, 99, 12, 117, 61, 71, 12, 60, 137, 0, 39, 135, 55, 101, 205, 223, 44, 73, 212, 115, 125, 253, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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