Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cada6ed3621321b959167ee44242c65b414ad8f12d0e3bade8b3500b458066ab

Tx prefix hash: c72cc5b616451c855e417b19f5e98c39aa849bd7d3c22851c0da34094f90525f
Tx public key: 6d332d4de41f9f079b17e3f981bfeee961ad247ce4b03b2cb21f026a0df13725
Timestamp: 1703109797 Timestamp [UCT]: 2023-12-20 22:03:17 Age [y:d:h:m:s]: 01:144:02:57:54
Block: 917546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364128 RingCT/type: yes/0
Extra: 016d332d4de41f9f079b17e3f981bfeee961ad247ce4b03b2cb21f026a0df13725021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d3b952ef056e397a61e4ef0efcfca10e73314aba0b9768924f45da7b452d7a0 0.600000000000 1375128 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": 917556, "vin": [ { "gen": { "height": 917546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d3b952ef056e397a61e4ef0efcfca10e73314aba0b9768924f45da7b452d7a0" } } ], "extra": [ 1, 109, 51, 45, 77, 228, 31, 159, 7, 155, 23, 227, 249, 129, 191, 238, 233, 97, 173, 36, 124, 228, 176, 59, 44, 178, 31, 2, 106, 13, 241, 55, 37, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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