Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b9a42a5ac8f449b697c18389b4f59f1cedfdee64570906966279dd41296034

Tx prefix hash: 03e3caae7f858d60d71d0f17ae39033d96d0ae87855393ba7533b7b13e4e046f
Tx public key: 6ad73e55f1b2901ae3e361ae8c4d8cccd06d37f60fc6add0d1e9b8b0f1633ecc
Timestamp: 1720535031 Timestamp [UCT]: 2024-07-09 14:23:51 Age [y:d:h:m:s]: 00:283:00:28:29
Block: 1061996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202219 RingCT/type: yes/0
Extra: 016ad73e55f1b2901ae3e361ae8c4d8cccd06d37f60fc6add0d1e9b8b0f1633ecc02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6565b0f8ad8ebaa35f0adc61eabf2af5bc22c167db83e1c550ef42a19f05802a 0.600000000000 1532495 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": 1062006, "vin": [ { "gen": { "height": 1061996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6565b0f8ad8ebaa35f0adc61eabf2af5bc22c167db83e1c550ef42a19f05802a" } } ], "extra": [ 1, 106, 215, 62, 85, 241, 178, 144, 26, 227, 227, 97, 174, 140, 77, 140, 204, 208, 109, 55, 246, 15, 198, 173, 208, 209, 233, 184, 176, 241, 99, 62, 204, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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