Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b811b0b6731d032c7569c61671854cf89f7b80e6c9cb796de1a347e03fe7856

Tx prefix hash: c9b18384ad34b27564d09450ba9885c45c8344d47b3d4081db2964206fdfae2e
Tx public key: 65f98321137389c262c031ad47228a792b7fe5b9c791d1ffac24d01945bfa728
Timestamp: 1695006330 Timestamp [UCT]: 2023-09-18 03:05:30 Age [y:d:h:m:s]: 01:250:22:39:57
Block: 850535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440477 RingCT/type: yes/0
Extra: 0165f98321137389c262c031ad47228a792b7fe5b9c791d1ffac24d01945bfa728021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.932877303000 dcy

stealth address amount amount idx
00: ff5f1aeb3b077d83213aa82fcdd696bb38ff02454a517ca690e1e963acd4c4c3 0.932877303000 1304259 of 0

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": 850545, "vin": [ { "gen": { "height": 850535 } } ], "vout": [ { "amount": 932877303, "target": { "key": "ff5f1aeb3b077d83213aa82fcdd696bb38ff02454a517ca690e1e963acd4c4c3" } } ], "extra": [ 1, 101, 249, 131, 33, 19, 115, 137, 194, 98, 192, 49, 173, 71, 34, 138, 121, 43, 127, 229, 185, 199, 145, 209, 255, 172, 36, 208, 25, 69, 191, 167, 40, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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