Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19412c04d8121a6c07d7005b8a4261e720f5d1010d310708798900a0c9d0ec63

Tx prefix hash: 616569bbc85718c4df36faf74294f8a3b5ddc5ffafe6e5aef7e047fda86eab60
Tx public key: c8e54451e0b1837bccbed3913f22529f346ee345f8d996ddcbcd3d0f04d92164
Timestamp: 1729011051 Timestamp [UCT]: 2024-10-15 16:50:51 Age [y:d:h:m:s]: 00:099:03:13:47
Block: 1132262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70820 RingCT/type: yes/0
Extra: 01c8e54451e0b1837bccbed3913f22529f346ee345f8d996ddcbcd3d0f04d92164021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f7ed0b2677205f8cb5ae229c24c9c462f87c13e4c3c7bfa7994dc97307217e1 0.600000000000 1615175 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": 1132272, "vin": [ { "gen": { "height": 1132262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f7ed0b2677205f8cb5ae229c24c9c462f87c13e4c3c7bfa7994dc97307217e1" } } ], "extra": [ 1, 200, 229, 68, 81, 224, 177, 131, 123, 204, 190, 211, 145, 63, 34, 82, 159, 52, 110, 227, 69, 248, 217, 150, 221, 203, 205, 61, 15, 4, 217, 33, 100, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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