Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd260ea877740758cff6c47ee3f5fdd73b7fe5662cdbd25a5d392760fdf9bd95

Tx prefix hash: 61a36d728a7f747394aabe783d652c208b57d89b9e0c9eb701f62bc21065da0e
Tx public key: 852f3ea509e9aeed272b9aec202881bd2f09bd41054a44b64037f87b3cd2868c
Timestamp: 1735759957 Timestamp [UCT]: 2025-01-01 19:32:37 Age [y:d:h:m:s]: 00:117:21:54:40
Block: 1188078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84084 RingCT/type: yes/0
Extra: 01852f3ea509e9aeed272b9aec202881bd2f09bd41054a44b64037f87b3cd2868c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b9ccf40baddccde97acd72a72ba3aaf3506f4fa05735272e59cfcd46e6759f2 0.600000000000 1674577 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": 1188088, "vin": [ { "gen": { "height": 1188078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b9ccf40baddccde97acd72a72ba3aaf3506f4fa05735272e59cfcd46e6759f2" } } ], "extra": [ 1, 133, 47, 62, 165, 9, 233, 174, 237, 39, 43, 154, 236, 32, 40, 129, 189, 47, 9, 189, 65, 5, 74, 68, 182, 64, 55, 248, 123, 60, 210, 134, 140, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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