Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5384064028508052d6922db60d9a78fc0004f16d70725c463d3e2b0346b2af32

Tx prefix hash: 84ab2a98f75a86a8c4b9f26a795165c96ebdf08ae3aa324c5df4a604effe3dd8
Tx public key: 4105a75dbfd5a60df7510d437d8942ecc3d0b0cff068a2a62be9c5a0511e2ea8
Timestamp: 1730108539 Timestamp [UCT]: 2024-10-28 09:42:19 Age [y:d:h:m:s]: 00:157:04:36:29
Block: 1141288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112171 RingCT/type: yes/0
Extra: 014105a75dbfd5a60df7510d437d8942ecc3d0b0cff068a2a62be9c5a0511e2ea802110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75bca7b98393a1eda2830149c0a5cd43edcb509c0499bc60f691ea35ac996d42 0.600000000000 1625095 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": 1141298, "vin": [ { "gen": { "height": 1141288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75bca7b98393a1eda2830149c0a5cd43edcb509c0499bc60f691ea35ac996d42" } } ], "extra": [ 1, 65, 5, 167, 93, 191, 213, 166, 13, 247, 81, 13, 67, 125, 137, 66, 236, 195, 208, 176, 207, 240, 104, 162, 166, 43, 233, 197, 160, 81, 30, 46, 168, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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