Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d026e7d59dfc6359fc645a1f9a2bd7b482e8f3132b34e119ce33ceec692fbd9

Tx prefix hash: 65e3b2d3292a2529bb073893e28bc3129eb091473cd30e2e975fada4b0647bc3
Tx public key: 19285e0a7d5625e56e67b1e8c60ce07aa440367b43b0bdef09e16ccb6830a4e1
Timestamp: 1707618476 Timestamp [UCT]: 2024-02-11 02:27:56 Age [y:d:h:m:s]: 00:316:04:16:56
Block: 954896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226401 RingCT/type: yes/0
Extra: 0119285e0a7d5625e56e67b1e8c60ce07aa440367b43b0bdef09e16ccb6830a4e102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6dae2d4107340effd0619d2845afdf97f7e5bc840e7e1e83643887a16d69cd 0.600000000000 1414178 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": 954906, "vin": [ { "gen": { "height": 954896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6dae2d4107340effd0619d2845afdf97f7e5bc840e7e1e83643887a16d69cd" } } ], "extra": [ 1, 25, 40, 94, 10, 125, 86, 37, 229, 110, 103, 177, 232, 198, 12, 224, 122, 164, 64, 54, 123, 67, 176, 189, 239, 9, 225, 108, 203, 104, 48, 164, 225, 2, 17, 0, 0, 0, 1, 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