Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c8ae40f69375be572d4529c79f3fa15d4f1573a76d5940dd3c9cf8c1bbffdfb

Tx prefix hash: 515907848beade9fb1ff017286d01b2f45b217b76e8d04499c7693c95fbcfb48
Tx public key: 21f6592770fcb194d099380f0670c3d1d3f98a48a7b2e9c54177a3786769f455
Timestamp: 1730879896 Timestamp [UCT]: 2024-11-06 07:58:16 Age [y:d:h:m:s]: 00:167:15:15:10
Block: 1147665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119649 RingCT/type: yes/0
Extra: 0121f6592770fcb194d099380f0670c3d1d3f98a48a7b2e9c54177a3786769f4550211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a85c3d9de11541c3371581cd4e37e1558ab61c883bdce965722fdafdd3cf2ade 0.600000000000 1632364 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": 1147675, "vin": [ { "gen": { "height": 1147665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a85c3d9de11541c3371581cd4e37e1558ab61c883bdce965722fdafdd3cf2ade" } } ], "extra": [ 1, 33, 246, 89, 39, 112, 252, 177, 148, 208, 153, 56, 15, 6, 112, 195, 209, 211, 249, 138, 72, 167, 178, 233, 197, 65, 119, 163, 120, 103, 105, 244, 85, 2, 17, 0, 0, 0, 7, 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