Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0bafb49499565f5fba049cebb2c10e891d13531cc0da0f534c1552e8cc438d

Tx prefix hash: f99aa222407ff4eaf58825d88f65364a4a349363cdf2944a150667b8ce3f0ece
Tx public key: 8f6ca1e88194756caa52b7e1411f6a1083245c247e4b1e3b5331c39a85574d84
Timestamp: 1737946946 Timestamp [UCT]: 2025-01-27 03:02:26 Age [y:d:h:m:s]: 00:328:15:35:37
Block: 1205951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232664 RingCT/type: yes/0
Extra: 018f6ca1e88194756caa52b7e1411f6a1083245c247e4b1e3b5331c39a85574d840211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be3f02d5de6c6526108a364c34e05935c4b8a41750f1281b01d346aa8efb13c 0.600000000000 1692650 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": 1205961, "vin": [ { "gen": { "height": 1205951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be3f02d5de6c6526108a364c34e05935c4b8a41750f1281b01d346aa8efb13c" } } ], "extra": [ 1, 143, 108, 161, 232, 129, 148, 117, 108, 170, 82, 183, 225, 65, 31, 106, 16, 131, 36, 92, 36, 126, 75, 30, 59, 83, 49, 195, 154, 133, 87, 77, 132, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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