Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b694f81ca01bbe6069fcd67070393da482378cf5f9ff1d7ffb514367c07945f5

Tx prefix hash: 1fe8cb1e4ef94840563b3515f67a0db582949b9fff1d43943fe37a289e344925
Tx public key: fa31f4f4598ea132d8149d79cea4eb77021fd6a0f06a9b9c16ae605e896f24e6
Timestamp: 1719721309 Timestamp [UCT]: 2024-06-30 04:21:49 Age [y:d:h:m:s]: 01:129:21:21:18
Block: 1055237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351364 RingCT/type: yes/0
Extra: 01fa31f4f4598ea132d8149d79cea4eb77021fd6a0f06a9b9c16ae605e896f24e60211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 755eb1d768dd836fdc03c5a66c81cc13e4aa5695c55d5253a415cb801e52756f 0.600000000000 1525634 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": 1055247, "vin": [ { "gen": { "height": 1055237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "755eb1d768dd836fdc03c5a66c81cc13e4aa5695c55d5253a415cb801e52756f" } } ], "extra": [ 1, 250, 49, 244, 244, 89, 142, 161, 50, 216, 20, 157, 121, 206, 164, 235, 119, 2, 31, 214, 160, 240, 106, 155, 156, 22, 174, 96, 94, 137, 111, 36, 230, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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