Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95958802cab03cddef5a5b33b25da32c8aac378341047a7ff72e6a96ddf257b

Tx prefix hash: 220f93e4096807a43c66d3471dca7567f43ce781d5ec35ca97f884bece73bf8b
Tx public key: ff3ed9b755e42fb807a6e9e4ec8adf319c00e46103cda27e3477397f27e32eb2
Timestamp: 1581966389 Timestamp [UCT]: 2020-02-17 19:06:29 Age [y:d:h:m:s]: 04:314:22:46:11
Block: 67003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117447 RingCT/type: yes/0
Extra: 01ff3ed9b755e42fb807a6e9e4ec8adf319c00e46103cda27e3477397f27e32eb20211000000134ac5aa02000000000000000000

1 output(s) for total of 368.154028971000 dcy

stealth address amount amount idx
00: 618271d0b8af920587dd519ce6603dcc77d5a06b090ad1db52d717ad03c0bd2d 368.154028971000 123384 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": 67013, "vin": [ { "gen": { "height": 67003 } } ], "vout": [ { "amount": 368154028971, "target": { "key": "618271d0b8af920587dd519ce6603dcc77d5a06b090ad1db52d717ad03c0bd2d" } } ], "extra": [ 1, 255, 62, 217, 183, 85, 228, 47, 184, 7, 166, 233, 228, 236, 138, 223, 49, 156, 0, 228, 97, 3, 205, 162, 126, 52, 119, 57, 127, 39, 227, 46, 178, 2, 17, 0, 0, 0, 19, 74, 197, 170, 2, 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