Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9c3cd4eb803f69d392b27411ca1e50dcd2e2c330b20251153fb4806815f1a99

Tx prefix hash: f68d2e7019925f8a323aaacacbb5fe27bc662a0fe0f2fcf2a961a6e4223cf5e3
Tx public key: f903ec059f9db46e3b8f45d082d2e3f8692cdba777a43345e3726379db93d895
Timestamp: 1706166980 Timestamp [UCT]: 2024-01-25 07:16:20 Age [y:d:h:m:s]: 01:075:15:13:05
Block: 942840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315151 RingCT/type: yes/0
Extra: 01f903ec059f9db46e3b8f45d082d2e3f8692cdba777a43345e3726379db93d89502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 878e3c5a422b4d1222a0fcd16f74aac0234e547bc744ad40c9632e22fb86d25d 0.600000000000 1401018 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": 942850, "vin": [ { "gen": { "height": 942840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "878e3c5a422b4d1222a0fcd16f74aac0234e547bc744ad40c9632e22fb86d25d" } } ], "extra": [ 1, 249, 3, 236, 5, 159, 157, 180, 110, 59, 143, 69, 208, 130, 210, 227, 248, 105, 44, 219, 167, 119, 164, 51, 69, 227, 114, 99, 121, 219, 147, 216, 149, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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