Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf969b292c0e366108875d6b62d48319bd18365b3e953d5046ecc451b59ed365

Tx prefix hash: 4a9f7cea4a943a41ee14231b59a54b58cc0d6a2098ff8b11925abafcfa7014c7
Tx public key: c504f5d54c1cbd42f3b3bc6144e1d8ee2281526418d28e5e2cc6d214f5c25838
Timestamp: 1721050331 Timestamp [UCT]: 2024-07-15 13:32:11 Age [y:d:h:m:s]: 00:100:07:04:10
Block: 1066279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71795 RingCT/type: yes/0
Extra: 01c504f5d54c1cbd42f3b3bc6144e1d8ee2281526418d28e5e2cc6d214f5c2583802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc56cc8adaf65335311d6af92f42a41126ae7b93e340744153d45b1e597061f 0.600000000000 1536852 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": 1066289, "vin": [ { "gen": { "height": 1066279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc56cc8adaf65335311d6af92f42a41126ae7b93e340744153d45b1e597061f" } } ], "extra": [ 1, 197, 4, 245, 213, 76, 28, 189, 66, 243, 179, 188, 97, 68, 225, 216, 238, 34, 129, 82, 100, 24, 210, 142, 94, 44, 198, 210, 20, 245, 194, 88, 56, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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