Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69123a884b2e3621f288cfe6aa698b6d63ded088c2b71e26ea8687d0558925b3

Tx prefix hash: 46927e19189ce4a2013c4876ed1add8929c4bb3f4b657054d2792d397f5e2b4a
Tx public key: 807030b2130f615eb4a42b7fa4255c33c079ebedadb18c49c99082df37ba5a69
Timestamp: 1717125901 Timestamp [UCT]: 2024-05-31 03:25:01 Age [y:d:h:m:s]: 00:311:01:24:36
Block: 1033729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222299 RingCT/type: yes/0
Extra: 01807030b2130f615eb4a42b7fa4255c33c079ebedadb18c49c99082df37ba5a6902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aff3bd1f674238f56f4b68c3f7092c830a2c0054cc5f1ab5204e9facf5728d4 0.600000000000 1502200 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": 1033739, "vin": [ { "gen": { "height": 1033729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aff3bd1f674238f56f4b68c3f7092c830a2c0054cc5f1ab5204e9facf5728d4" } } ], "extra": [ 1, 128, 112, 48, 178, 19, 15, 97, 94, 180, 164, 43, 127, 164, 37, 92, 51, 192, 121, 235, 237, 173, 177, 140, 73, 201, 144, 130, 223, 55, 186, 90, 105, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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