Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64f232cb7d74e16ce6f171709a05c1c217aa32f26e496d65174c34b38c4a90a

Tx prefix hash: 633296c2278d31d54cc87cfde523e4a2374916751c939111f5036cb6e6c680b1
Tx public key: d14b7ca2aa8950cf85b586a6fefd6553957f135e3130a4009738c5a5ef24d4f3
Timestamp: 1749216125 Timestamp [UCT]: 2025-06-06 13:22:05 Age [y:d:h:m:s]: 00:167:19:18:14
Block: 1299221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117603 RingCT/type: yes/0
Extra: 01d14b7ca2aa8950cf85b586a6fefd6553957f135e3130a4009738c5a5ef24d4f3021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07744700f778a9a746dcb1295734b37c5e5e1ab5307ef28bb2c55268224411f 0.600000000000 1786758 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": 1299231, "vin": [ { "gen": { "height": 1299221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07744700f778a9a746dcb1295734b37c5e5e1ab5307ef28bb2c55268224411f" } } ], "extra": [ 1, 209, 75, 124, 162, 170, 137, 80, 207, 133, 181, 134, 166, 254, 253, 101, 83, 149, 127, 19, 94, 49, 48, 164, 0, 151, 56, 197, 165, 239, 36, 212, 243, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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