Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3cd0878697df255e4c7c24f2da1ecee95554df2320c9f4bcaf711bc0055b32

Tx prefix hash: 35cb3dd3705936042e854213684a23f3c75f20fea27f350231e72d35810c43b8
Tx public key: 55b8d8b77ad406b4c6098be326cd85cf76c9e5559ebb80c3c6a24a66e65d2677
Timestamp: 1723928508 Timestamp [UCT]: 2024-08-17 21:01:48 Age [y:d:h:m:s]: 00:252:17:38:43
Block: 1090136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180511 RingCT/type: yes/0
Extra: 0155b8d8b77ad406b4c6098be326cd85cf76c9e5559ebb80c3c6a24a66e65d2677021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c1365d78191e2abb4e3e08a615f99df497963b9b6acc10fad651dbf9738d87d 0.600000000000 1564759 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": 1090146, "vin": [ { "gen": { "height": 1090136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c1365d78191e2abb4e3e08a615f99df497963b9b6acc10fad651dbf9738d87d" } } ], "extra": [ 1, 85, 184, 216, 183, 122, 212, 6, 180, 198, 9, 139, 227, 38, 205, 133, 207, 118, 201, 229, 85, 158, 187, 128, 195, 198, 162, 74, 102, 230, 93, 38, 119, 2, 17, 0, 0, 0, 6, 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