Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6517f8a492fcf9992d7005c900ee97356c582001905270f8b44b73f7dd4b058

Tx prefix hash: 8eac2da551eb7f756fd63674b9b5a2f780ecb0769a6e4f1de4f4de9cd29026d8
Tx public key: 9cb4d91a14fb694688eed924fee1db009be97262b9c5a4845b48bc7207cba14b
Timestamp: 1711419419 Timestamp [UCT]: 2024-03-26 02:16:59 Age [y:d:h:m:s]: 01:018:06:09:37
Block: 986442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274003 RingCT/type: yes/0
Extra: 019cb4d91a14fb694688eed924fee1db009be97262b9c5a4845b48bc7207cba14b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b08e39e5a9282c53d38b230f45e5ce94dc40c79afdc6ad75c56b8e08009b55 0.600000000000 1446671 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": 986452, "vin": [ { "gen": { "height": 986442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b08e39e5a9282c53d38b230f45e5ce94dc40c79afdc6ad75c56b8e08009b55" } } ], "extra": [ 1, 156, 180, 217, 26, 20, 251, 105, 70, 136, 238, 217, 36, 254, 225, 219, 0, 155, 233, 114, 98, 185, 197, 164, 132, 91, 72, 188, 114, 7, 203, 161, 75, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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