Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f03e1cb7ee990d328c0034c3c09eb55558ab0479ce0b72df852c04cf978bef81

Tx prefix hash: 270de248fce7303cf9b21240a61b9003bddf081a1675415498fef27ae88c06e2
Tx public key: 2717e9b61ff517b5570ab00173e5f7b6fba2d9541366f3c78f08819a881f0777
Timestamp: 1704779411 Timestamp [UCT]: 2024-01-09 05:50:11 Age [y:d:h:m:s]: 01:082:07:53:24
Block: 931342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319955 RingCT/type: yes/0
Extra: 012717e9b61ff517b5570ab00173e5f7b6fba2d9541366f3c78f08819a881f07770211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5bdb733b6983a5b5ae930186e500fdf6ce5563bebe07ac39c7e1901f2369789 0.600000000000 1389240 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": 931352, "vin": [ { "gen": { "height": 931342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5bdb733b6983a5b5ae930186e500fdf6ce5563bebe07ac39c7e1901f2369789" } } ], "extra": [ 1, 39, 23, 233, 182, 31, 245, 23, 181, 87, 10, 176, 1, 115, 229, 247, 182, 251, 162, 217, 84, 19, 102, 243, 199, 143, 8, 129, 154, 136, 31, 7, 119, 2, 17, 0, 0, 0, 1, 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