Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976c90588ae79e81fa0bb7259190dd2fa7686c9ca0ce6d1ca7d0cf19f371d819

Tx prefix hash: 7e4e73dc907d47809d047603718db42d4a5a33fce5481de75513640fb8e87e5e
Tx public key: 74dc7780b9cdaef68035eecf1ec72c2544413e84ff7e8d891ce29b54df90ea0b
Timestamp: 1733720597 Timestamp [UCT]: 2024-12-09 05:03:17 Age [y:d:h:m:s]: 00:103:00:12:35
Block: 1171202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73409 RingCT/type: yes/0
Extra: 0174dc7780b9cdaef68035eecf1ec72c2544413e84ff7e8d891ce29b54df90ea0b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c884947780b5e39244f713f986665caaa3a291a65f0dab8946a00a9c360d75f2 0.600000000000 1656941 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": 1171212, "vin": [ { "gen": { "height": 1171202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c884947780b5e39244f713f986665caaa3a291a65f0dab8946a00a9c360d75f2" } } ], "extra": [ 1, 116, 220, 119, 128, 185, 205, 174, 246, 128, 53, 238, 207, 30, 199, 44, 37, 68, 65, 62, 132, 255, 126, 141, 137, 28, 226, 155, 84, 223, 144, 234, 11, 2, 17, 0, 0, 0, 2, 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