Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75e94425d40f0c0fb93b9a2b3740d4f792b91880aa85bce2b57741a6666edded

Tx prefix hash: 1ba4d0aeb4893ff2b47eea5cc17be0201055dee8004e50c11b5127845f66d851
Tx public key: be3884443e0963c9051b319a0f5ef2b8d9354fdd9eaddf4bbfa173d85eaa3c70
Timestamp: 1705929475 Timestamp [UCT]: 2024-01-22 13:17:55 Age [y:d:h:m:s]: 01:343:16:41:49
Block: 940870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504531 RingCT/type: yes/0
Extra: 01be3884443e0963c9051b319a0f5ef2b8d9354fdd9eaddf4bbfa173d85eaa3c7002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45308e556047ed88abafd61ab27da915e11c3d66cfd3974609aa8c797c94e14b 0.600000000000 1399010 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": 940880, "vin": [ { "gen": { "height": 940870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45308e556047ed88abafd61ab27da915e11c3d66cfd3974609aa8c797c94e14b" } } ], "extra": [ 1, 190, 56, 132, 68, 62, 9, 99, 201, 5, 27, 49, 154, 15, 94, 242, 184, 217, 53, 79, 221, 158, 173, 223, 75, 191, 161, 115, 216, 94, 170, 60, 112, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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