Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4426837d5d6893ce692712cde955933699cb056b69dc1ee52672d13c4f9f440e

Tx prefix hash: b73c19ab4c1e4741a706e1e460ba400f349d85e52a9cfb41f4760c42fbf3a2a9
Tx public key: df66d5408274b65e2fc517ed9e0a8514fc40443766cb540f11a8afc8f9efa3bc
Timestamp: 1706862712 Timestamp [UCT]: 2024-02-02 08:31:52 Age [y:d:h:m:s]: 00:348:14:26:06
Block: 948632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249559 RingCT/type: yes/0
Extra: 01df66d5408274b65e2fc517ed9e0a8514fc40443766cb540f11a8afc8f9efa3bc02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 487862bc6a956c57d693649853778b7e21bb4218ac4c71886baca1ed1ec0ea00 0.600000000000 1407080 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": 948642, "vin": [ { "gen": { "height": 948632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "487862bc6a956c57d693649853778b7e21bb4218ac4c71886baca1ed1ec0ea00" } } ], "extra": [ 1, 223, 102, 213, 64, 130, 116, 182, 94, 47, 197, 23, 237, 158, 10, 133, 20, 252, 64, 68, 55, 102, 203, 84, 15, 17, 168, 175, 200, 249, 239, 163, 188, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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