Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d5115c9dd1f267ef19d778eb5bea16ad21efff735cc103acf46beccdb1b7044

Tx prefix hash: 37dee802a6c4d16d38da532ccd5ab85dbd8338a0aba9fcdb7d512cadaf6c24e3
Tx public key: 86adcbef79ffe7f3cea90a62965400febae1d5a30965a8e2f531c58701b7c364
Timestamp: 1711283467 Timestamp [UCT]: 2024-03-24 12:31:07 Age [y:d:h:m:s]: 01:036:12:00:49
Block: 985315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287061 RingCT/type: yes/0
Extra: 0186adcbef79ffe7f3cea90a62965400febae1d5a30965a8e2f531c58701b7c3640211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2ae64afef26e0c8bee9d0695e00c43ab7fa0987aa5a0ca41b6fe0f16ea8bf2 0.600000000000 1445524 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": 985325, "vin": [ { "gen": { "height": 985315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2ae64afef26e0c8bee9d0695e00c43ab7fa0987aa5a0ca41b6fe0f16ea8bf2" } } ], "extra": [ 1, 134, 173, 203, 239, 121, 255, 231, 243, 206, 169, 10, 98, 150, 84, 0, 254, 186, 225, 213, 163, 9, 101, 168, 226, 245, 49, 197, 135, 1, 183, 195, 100, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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