Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b051c56463d7536e634553390e447d2ec8e3c4b171940cf7a6c5a4522713946a

Tx prefix hash: c3de0d4c6c8d5849bf844829eaf07beda5113bde6abce18f5f809d06ed6bf712
Tx public key: c876dc2fb000373b6d40fb8c010ebe3705dd4188957f21ae781326e2c84a8365
Timestamp: 1705434549 Timestamp [UCT]: 2024-01-16 19:49:09 Age [y:d:h:m:s]: 01:038:12:27:59
Block: 936783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288583 RingCT/type: yes/0
Extra: 01c876dc2fb000373b6d40fb8c010ebe3705dd4188957f21ae781326e2c84a836502110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06df700aa66045ad406052f38bffcac55e418b0ff7f8fe44577aebf522964f7 0.600000000000 1394823 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": 936793, "vin": [ { "gen": { "height": 936783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06df700aa66045ad406052f38bffcac55e418b0ff7f8fe44577aebf522964f7" } } ], "extra": [ 1, 200, 118, 220, 47, 176, 0, 55, 59, 109, 64, 251, 140, 1, 14, 190, 55, 5, 221, 65, 136, 149, 127, 33, 174, 120, 19, 38, 226, 200, 74, 131, 101, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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