Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b59949007024b668355ad040b2e424a59415ab4a5ed9c91ce2623f7edb1fb823

Tx prefix hash: de28669eb01542f70d689d839e7677cf201fc4df2f92245be1c2232e125b6232
Tx public key: 02177fdcb6ce2a9cbc5e5414c5f12adc6ca972f71f85c96e9cb10e5a0376169e
Timestamp: 1659647215 Timestamp [UCT]: 2022-08-04 21:06:55 Age [y:d:h:m:s]: 02:228:00:58:56
Block: 558788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 684207 RingCT/type: yes/0
Extra: 0102177fdcb6ce2a9cbc5e5414c5f12adc6ca972f71f85c96e9cb10e5a0376169e0211000000016570b1ef000000000000000000

1 output(s) for total of 8.639796463000 dcy

stealth address amount amount idx
00: 67b17b98b9ede1fd700e8ad15997b914295ec57016f2a2633d704a165955001b 8.639796463000 990886 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": 558798, "vin": [ { "gen": { "height": 558788 } } ], "vout": [ { "amount": 8639796463, "target": { "key": "67b17b98b9ede1fd700e8ad15997b914295ec57016f2a2633d704a165955001b" } } ], "extra": [ 1, 2, 23, 127, 220, 182, 206, 42, 156, 188, 94, 84, 20, 197, 241, 42, 220, 108, 169, 114, 247, 31, 133, 201, 110, 156, 177, 14, 90, 3, 118, 22, 158, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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