Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca299d3bc74a83363f37842e5c656114b936a90211a41d692da5954559f2919

Tx prefix hash: 99b591b77dd3e403037cd9223303adc6388284c9a5050108de4f0b30bfcfffce
Tx public key: 032b389e0ec7e01072a944ab0c8b025d893c6dada4f07d9261949816b232d1cd
Timestamp: 1721792519 Timestamp [UCT]: 2024-07-24 03:41:59 Age [y:d:h:m:s]: 00:308:07:37:26
Block: 1072406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220326 RingCT/type: yes/0
Extra: 01032b389e0ec7e01072a944ab0c8b025d893c6dada4f07d9261949816b232d1cd02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b5d2bc7cb40a7a9b4a19a8ecd7d869cbd72fe1536f8d3a07b9cd5bcf9f53c32 0.600000000000 1544875 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": 1072416, "vin": [ { "gen": { "height": 1072406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5d2bc7cb40a7a9b4a19a8ecd7d869cbd72fe1536f8d3a07b9cd5bcf9f53c32" } } ], "extra": [ 1, 3, 43, 56, 158, 14, 199, 224, 16, 114, 169, 68, 171, 12, 139, 2, 93, 137, 60, 109, 173, 164, 240, 125, 146, 97, 148, 152, 22, 178, 50, 209, 205, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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