Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44e9d3525703a6691959711dbe1aa4c9b53dc683ab082f86637ecc49bbe367f

Tx prefix hash: 36306b67ea0ad17702abf09efef28f66c72713007023dfe579ea7c3b54829e9f
Tx public key: d883a33f22695fca8e95e30d5a97fdb07c0b16899822f8bcba93aa6318bbe24d
Timestamp: 1698919823 Timestamp [UCT]: 2023-11-02 10:10:23 Age [y:d:h:m:s]: 01:156:07:19:00
Block: 883003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372688 RingCT/type: yes/0
Extra: 01d883a33f22695fca8e95e30d5a97fdb07c0b16899822f8bcba93aa6318bbe24d021100000005faf35c9c000000000000000000

1 output(s) for total of 0.728189676000 dcy

stealth address amount amount idx
00: 9f2a71348f6ab53ef2350dff8f067e690b9d6fb720e2b72d397d39147f3b137e 0.728189676000 1338685 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": 883013, "vin": [ { "gen": { "height": 883003 } } ], "vout": [ { "amount": 728189676, "target": { "key": "9f2a71348f6ab53ef2350dff8f067e690b9d6fb720e2b72d397d39147f3b137e" } } ], "extra": [ 1, 216, 131, 163, 63, 34, 105, 95, 202, 142, 149, 227, 13, 90, 151, 253, 176, 124, 11, 22, 137, 152, 34, 248, 188, 186, 147, 170, 99, 24, 187, 226, 77, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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