Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4fc77ebe1bb17eaeac42f1f5b0f9c7533d835845313ccdce5d66cdb25af551e

Tx prefix hash: b7290c3f1db9deac1536d88ef8cf25f8cc73fbafb78f64b352aed34fbcd2dd32
Tx public key: a38d7e3f6a12f1659e7fbd6482c339abc059c6bfc81356a6325765d7eb7616ac
Timestamp: 1729563254 Timestamp [UCT]: 2024-10-22 02:14:14 Age [y:d:h:m:s]: 00:033:10:03:13
Block: 1136799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23882 RingCT/type: yes/0
Extra: 01a38d7e3f6a12f1659e7fbd6482c339abc059c6bfc81356a6325765d7eb7616ac021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6ccc73355ac48b62b708506521a4fbfcf658b4a709f5c14914fccf2df75c56a 0.600000000000 1620174 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": 1136809, "vin": [ { "gen": { "height": 1136799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6ccc73355ac48b62b708506521a4fbfcf658b4a709f5c14914fccf2df75c56a" } } ], "extra": [ 1, 163, 141, 126, 63, 106, 18, 241, 101, 158, 127, 189, 100, 130, 195, 57, 171, 192, 89, 198, 191, 200, 19, 86, 166, 50, 87, 101, 215, 235, 118, 22, 172, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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