Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aac9800257b020e3fa6ea3edb2684701ed9ea0ab771b652d3f804d4baf04e996

Tx prefix hash: a37df073fc10d4f50ffd8c525654486d2938933ee2ef34acbd1e872a5854575c
Tx public key: c05b62ac6433c4c7274db35c4ad1cb8435a1761fda5537aba56252a7bdb28815
Timestamp: 1634938984 Timestamp [UCT]: 2021-10-22 21:43:04 Age [y:d:h:m:s]: 03:081:01:37:51
Block: 358376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836250 RingCT/type: yes/0
Extra: 01c05b62ac6433c4c7274db35c4ad1cb8435a1761fda5537aba56252a7bdb28815021100000001fdc024ec000000000000000000

1 output(s) for total of 39.863595533000 dcy

stealth address amount amount idx
00: 639c5ef65b0df3150180d72222c4fb2e45a79acfcb6af605a1662ac96897d57d 39.863595533000 730255 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": 358386, "vin": [ { "gen": { "height": 358376 } } ], "vout": [ { "amount": 39863595533, "target": { "key": "639c5ef65b0df3150180d72222c4fb2e45a79acfcb6af605a1662ac96897d57d" } } ], "extra": [ 1, 192, 91, 98, 172, 100, 51, 196, 199, 39, 77, 179, 92, 74, 209, 203, 132, 53, 161, 118, 31, 218, 85, 55, 171, 165, 98, 82, 167, 189, 178, 136, 21, 2, 17, 0, 0, 0, 1, 253, 192, 36, 236, 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