Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b75e21b941c47bb62a2d84121da6af9838ac3292cd2ef41fbeb6122d3998c597

Tx prefix hash: 0a3c387f68fc9aea34d2778f0639af8a4071a53efb39c055b3a523062e81d9e8
Tx public key: 0dd2a2f7306b4395e79f25bff32bb065a5451090e8f14b289858514e9a2e6696
Timestamp: 1733024857 Timestamp [UCT]: 2024-12-01 03:47:37 Age [y:d:h:m:s]: 00:127:22:00:37
Block: 1165441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91208 RingCT/type: yes/0
Extra: 010dd2a2f7306b4395e79f25bff32bb065a5451090e8f14b289858514e9a2e66960211000000028f9f0b94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b56026a2f16fc1f8b01a246c7b900922513a74f56bfb7807876a80433d49fd4 0.600000000000 1651116 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": 1165451, "vin": [ { "gen": { "height": 1165441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b56026a2f16fc1f8b01a246c7b900922513a74f56bfb7807876a80433d49fd4" } } ], "extra": [ 1, 13, 210, 162, 247, 48, 107, 67, 149, 231, 159, 37, 191, 243, 43, 176, 101, 165, 69, 16, 144, 232, 241, 75, 40, 152, 88, 81, 78, 154, 46, 102, 150, 2, 17, 0, 0, 0, 2, 143, 159, 11, 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