Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6673dd8cb048f26b29938a2dbb229b16d0320d2dbcc537c6414644581ea1c0

Tx prefix hash: e46c7a6ec90d4e061205fe2c1f1a56868e6cc81d7a6770da3aac5f8a4e0b4b5f
Tx public key: d3f8c68850beb9cb859a34eee30ab6584f84ef979366e04e2dc80ba9a336467e
Timestamp: 1717067940 Timestamp [UCT]: 2024-05-30 11:19:00 Age [y:d:h:m:s]: 01:161:00:45:13
Block: 1033246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373674 RingCT/type: yes/0
Extra: 01d3f8c68850beb9cb859a34eee30ab6584f84ef979366e04e2dc80ba9a336467e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3ad3a2a3567b8f88279b5c23adb6e866b6efeea9f46aeb03de93f729a98c54e 0.600000000000 1501709 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": 1033256, "vin": [ { "gen": { "height": 1033246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3ad3a2a3567b8f88279b5c23adb6e866b6efeea9f46aeb03de93f729a98c54e" } } ], "extra": [ 1, 211, 248, 198, 136, 80, 190, 185, 203, 133, 154, 52, 238, 227, 10, 182, 88, 79, 132, 239, 151, 147, 102, 224, 78, 45, 200, 11, 169, 163, 54, 70, 126, 2, 17, 0, 0, 0, 2, 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