Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6069c36b7e857ec021c1289930432ff6132c2042e321057028e8aa414c12e4e

Tx prefix hash: 8fc3f25c6812e1a2922c468a5cf50a19bd2aea63c0256fd8083781287266494e
Tx public key: 2b4f3a364dbd1508ee48f88f29d8805a900e90d7b23b8bab6b98f3521df06016
Timestamp: 1723504122 Timestamp [UCT]: 2024-08-12 23:08:42 Age [y:d:h:m:s]: 00:216:11:59:24
Block: 1086603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154629 RingCT/type: yes/0
Extra: 012b4f3a364dbd1508ee48f88f29d8805a900e90d7b23b8bab6b98f3521df0601602110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05e4a8a6fa8b494ac1bb406567b3ba96c8ea9932d1f1af8b8bf0226329f22933 0.600000000000 1561200 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": 1086613, "vin": [ { "gen": { "height": 1086603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e4a8a6fa8b494ac1bb406567b3ba96c8ea9932d1f1af8b8bf0226329f22933" } } ], "extra": [ 1, 43, 79, 58, 54, 77, 189, 21, 8, 238, 72, 248, 143, 41, 216, 128, 90, 144, 14, 144, 215, 178, 59, 139, 171, 107, 152, 243, 82, 29, 240, 96, 22, 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