Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 789e78b08a186fb917c6cab9e926df716e3cf6993614a5ea64fc1f3dc71e404b

Tx prefix hash: 8d3ee2a3eb8bd055334c58195106247d733b9b55b6476a2142c556aab57df3ee
Tx public key: b100a1ba2e0de28cefde246a9bfe852c5efe4516a118577afb612e77c53f03bf
Timestamp: 1704599032 Timestamp [UCT]: 2024-01-07 03:43:52 Age [y:d:h:m:s]: 01:319:06:48:46
Block: 929845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487044 RingCT/type: yes/0
Extra: 01b100a1ba2e0de28cefde246a9bfe852c5efe4516a118577afb612e77c53f03bf02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9d15e721f3432dfeb5b3e9f99ecc58e8b810d520b09c415e4746d60ac5f70d8 0.600000000000 1387721 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": 929855, "vin": [ { "gen": { "height": 929845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9d15e721f3432dfeb5b3e9f99ecc58e8b810d520b09c415e4746d60ac5f70d8" } } ], "extra": [ 1, 177, 0, 161, 186, 46, 13, 226, 140, 239, 222, 36, 106, 155, 254, 133, 44, 94, 254, 69, 22, 161, 24, 87, 122, 251, 97, 46, 119, 197, 63, 3, 191, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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