Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ce9820e6a6b0a8913fa3abcb870c450dde3cdd2f125e271be9b7efad9ded10

Tx prefix hash: cd188a5a4083dd0d96c7e60cb74d7afe34aee556012100e94ce062c4d328b0b9
Tx public key: d16f68d355ad6cd3878aa46de5fc7a3fdf497de5bca662e7c391f3b9dab84da7
Timestamp: 1722739298 Timestamp [UCT]: 2024-08-04 02:41:38 Age [y:d:h:m:s]: 00:301:19:31:03
Block: 1080270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215636 RingCT/type: yes/0
Extra: 01d16f68d355ad6cd3878aa46de5fc7a3fdf497de5bca662e7c391f3b9dab84da702110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da77317442a96899bc4eb6e9c0f4dd4a5232ed88fa42110d0d263083dc204448 0.600000000000 1553559 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": 1080280, "vin": [ { "gen": { "height": 1080270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da77317442a96899bc4eb6e9c0f4dd4a5232ed88fa42110d0d263083dc204448" } } ], "extra": [ 1, 209, 111, 104, 211, 85, 173, 108, 211, 135, 138, 164, 109, 229, 252, 122, 63, 223, 73, 125, 229, 188, 166, 98, 231, 195, 145, 243, 185, 218, 184, 77, 167, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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