Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0842f426e12f4982c67405ff56a51f54a0ea846f58cb995fbabdfbab1636f846

Tx prefix hash: 06593affffe630677a7c0af3050351f2e16dfd12ddf30c8fb79a57b3f29fcce5
Tx public key: 18436592884a10a49aa50c3fbd83b5541edfb3265eba4cc46d8ec0b0cd6c66af
Timestamp: 1725364223 Timestamp [UCT]: 2024-09-03 11:50:23 Age [y:d:h:m:s]: 00:050:08:58:41
Block: 1102032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36052 RingCT/type: yes/0
Extra: 0118436592884a10a49aa50c3fbd83b5541edfb3265eba4cc46d8ec0b0cd6c66af02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c19d2ab0d4fa535a3c16b0b7f7ecc1b378da5ff6c89d407ee4e181c6af4c696 0.600000000000 1578307 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": 1102042, "vin": [ { "gen": { "height": 1102032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c19d2ab0d4fa535a3c16b0b7f7ecc1b378da5ff6c89d407ee4e181c6af4c696" } } ], "extra": [ 1, 24, 67, 101, 146, 136, 74, 16, 164, 154, 165, 12, 63, 189, 131, 181, 84, 30, 223, 179, 38, 94, 186, 76, 196, 109, 142, 192, 176, 205, 108, 102, 175, 2, 17, 0, 0, 0, 14, 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