Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c75bac53124adadbacfb026d45780950946f08b409468dbce3c96160729748c

Tx prefix hash: 17370f9eacec5d56f29298f382fd117ae07c779aca8c93bb4a36c0b5539d0358
Tx public key: b81cc402a0dc41129d79eb59c8879c0f94dd585c8901cfd8fdbe98f8e95b5fe2
Timestamp: 1701865043 Timestamp [UCT]: 2023-12-06 12:17:23 Age [y:d:h:m:s]: 01:106:11:38:29
Block: 907206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337248 RingCT/type: yes/0
Extra: 01b81cc402a0dc41129d79eb59c8879c0f94dd585c8901cfd8fdbe98f8e95b5fe2021100000001c5452960000000000000000000

1 output(s) for total of 0.605410426000 dcy

stealth address amount amount idx
00: fef473b5cefcf15fdcde405061308b795ad4d29fe815bb476840afebbcb55d9d 0.605410426000 1364187 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": 907216, "vin": [ { "gen": { "height": 907206 } } ], "vout": [ { "amount": 605410426, "target": { "key": "fef473b5cefcf15fdcde405061308b795ad4d29fe815bb476840afebbcb55d9d" } } ], "extra": [ 1, 184, 28, 196, 2, 160, 220, 65, 18, 157, 121, 235, 89, 200, 135, 156, 15, 148, 221, 88, 92, 137, 1, 207, 216, 253, 190, 152, 248, 233, 91, 95, 226, 2, 17, 0, 0, 0, 1, 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