Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1b3f046621ee177251c26b7f24302cfe7427cd8201354f0fa87dbea93a016c3

Tx prefix hash: 5f36435a93f3527ce67e0c5e8a6ca8c97e7faa5e29c81570083e601b646b7fb9
Tx public key: da894f9c01e4360ca82e1eb4c0ca09c85ad5718f3e0894365b838a08f106005f
Timestamp: 1732011252 Timestamp [UCT]: 2024-11-19 10:14:12 Age [y:d:h:m:s]: 00:004:16:44:48
Block: 1157043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3362 RingCT/type: yes/0
Extra: 01da894f9c01e4360ca82e1eb4c0ca09c85ad5718f3e0894365b838a08f106005f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b6e1af56b01fd12fc219ae2a514078e2d00ece9c0e8ebc9ea583c2251c52360 0.600000000000 1642666 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": 1157053, "vin": [ { "gen": { "height": 1157043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b6e1af56b01fd12fc219ae2a514078e2d00ece9c0e8ebc9ea583c2251c52360" } } ], "extra": [ 1, 218, 137, 79, 156, 1, 228, 54, 12, 168, 46, 30, 180, 192, 202, 9, 200, 90, 213, 113, 143, 62, 8, 148, 54, 91, 131, 138, 8, 241, 6, 0, 95, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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