Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 137c17ac87ad8aa23d741e0587f8f17dcbc6f99e4bbca745892b49db9d8ca977

Tx prefix hash: 7197e33108ef7883e60f2253edda20926a30aeae70ecfbfae4f99bf5e51aea0b
Tx public key: 0e860d0c83f3c0f1f462a999007f2480c889478c385f47a907f60c33eadf7adc
Timestamp: 1583931489 Timestamp [UCT]: 2020-03-11 12:58:09 Age [y:d:h:m:s]: 04:292:14:27:17
Block: 80414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104319 RingCT/type: yes/0
Extra: 010e860d0c83f3c0f1f462a999007f2480c889478c385f47a907f60c33eadf7adc02110000001c4ac5aa02000000000000000000

1 output(s) for total of 332.349250106000 dcy

stealth address amount amount idx
00: c501dde376471ee7d6e29d96ae8bd4bce2436c4d3a6a65404897ae0a74c9d47e 332.349250106000 147186 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": 80424, "vin": [ { "gen": { "height": 80414 } } ], "vout": [ { "amount": 332349250106, "target": { "key": "c501dde376471ee7d6e29d96ae8bd4bce2436c4d3a6a65404897ae0a74c9d47e" } } ], "extra": [ 1, 14, 134, 13, 12, 131, 243, 192, 241, 244, 98, 169, 153, 0, 127, 36, 128, 200, 137, 71, 140, 56, 95, 71, 169, 7, 246, 12, 51, 234, 223, 122, 220, 2, 17, 0, 0, 0, 28, 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