Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d406b4ae47f1391df6abe150ca1d0f64d8e29ed5a96e1bf2afc22faa7214c3

Tx prefix hash: 90309a301619b0beb6e994b9fc752ae8bf93a33807a478350a2b750a013c5bde
Tx public key: d6789eea365c8948248c59bbbe6b2a6c6b8f4d9131ca01ada4f0d5021b6ed14a
Timestamp: 1703416145 Timestamp [UCT]: 2023-12-24 11:09:05 Age [y:d:h:m:s]: 01:102:14:24:16
Block: 920071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334439 RingCT/type: yes/0
Extra: 01d6789eea365c8948248c59bbbe6b2a6c6b8f4d9131ca01ada4f0d5021b6ed14a021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f59ebced939471d4da157fa98475696587ed1837bf0a7fb43362e2df251983f 0.600000000000 1377749 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": 920081, "vin": [ { "gen": { "height": 920071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f59ebced939471d4da157fa98475696587ed1837bf0a7fb43362e2df251983f" } } ], "extra": [ 1, 214, 120, 158, 234, 54, 92, 137, 72, 36, 140, 89, 187, 190, 107, 42, 108, 107, 143, 77, 145, 49, 202, 1, 173, 164, 240, 213, 2, 27, 110, 209, 74, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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