Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af40b95e9cea087e3e77f694c582ca02510c18bcc313f6f2950d8ea6617621e1

Tx prefix hash: ec7f4ee762f0b9d8f31fcb2dddde9d428a25141d3e49d0eadd12ebae24899ddc
Tx public key: c1fe699e25ba7a626de5cdfba666992c9299091f23da77613f59d1fc009c6c88
Timestamp: 1579041274 Timestamp [UCT]: 2020-01-14 22:34:34 Age [y:d:h:m:s]: 04:317:21:19:50
Block: 45647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116691 RingCT/type: yes/0
Extra: 01c1fe699e25ba7a626de5cdfba666992c9299091f23da77613f59d1fc009c6c88021100000124b221b3d1000000000000000000

1 output(s) for total of 433.264772641000 dcy

stealth address amount amount idx
00: d5a19e162a7d81c24ecefd0364cba72a17fbac8a676791d8e99314aa3b1c49ea 433.264772641000 83515 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": 45657, "vin": [ { "gen": { "height": 45647 } } ], "vout": [ { "amount": 433264772641, "target": { "key": "d5a19e162a7d81c24ecefd0364cba72a17fbac8a676791d8e99314aa3b1c49ea" } } ], "extra": [ 1, 193, 254, 105, 158, 37, 186, 122, 98, 109, 229, 205, 251, 166, 102, 153, 44, 146, 153, 9, 31, 35, 218, 119, 97, 63, 89, 209, 252, 0, 156, 108, 136, 2, 17, 0, 0, 1, 36, 178, 33, 179, 209, 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