Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fed492276e6fcfb9cd7b0eb43a73f87c1bcf55d232bb61d0ef6a4ce928e013fa

Tx prefix hash: f9b84a50902070f9719adf1bea164817407b373bf38567511c59d374c27033c7
Tx public key: 1888f775e9cad76e47c68c1849e79cff0254f49bcc4a52dbb2b835a6a0986279
Timestamp: 1696931428 Timestamp [UCT]: 2023-10-10 09:50:28 Age [y:d:h:m:s]: 01:179:16:36:34
Block: 866516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389435 RingCT/type: yes/0
Extra: 011888f775e9cad76e47c68c1849e79cff0254f49bcc4a52dbb2b835a6a0986279021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.825796079000 dcy

stealth address amount amount idx
00: aa134d538be74b9d5f4ad2a5a7d3341cfdad6ae050fb3c72c51618c7745937bc 0.825796079000 1321118 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": 866526, "vin": [ { "gen": { "height": 866516 } } ], "vout": [ { "amount": 825796079, "target": { "key": "aa134d538be74b9d5f4ad2a5a7d3341cfdad6ae050fb3c72c51618c7745937bc" } } ], "extra": [ 1, 24, 136, 247, 117, 233, 202, 215, 110, 71, 198, 140, 24, 73, 231, 156, 255, 2, 84, 244, 155, 204, 74, 82, 219, 178, 184, 53, 166, 160, 152, 98, 121, 2, 17, 0, 0, 0, 3, 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