Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b016a8318cb8bb4ae4744c5574deb3054c154401f4e540ce261147ecd70d6e

Tx prefix hash: a17a6d96394359d9a51731bcab91ffefa656e22aea3947f719ac17c9b89849a8
Tx public key: 74cc83b308e81d4be384a717b371ddb8b5dd5ce78d02275a7e0a10fe40b1e657
Timestamp: 1706171049 Timestamp [UCT]: 2024-01-25 08:24:09 Age [y:d:h:m:s]: 00:364:23:07:38
Block: 942874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261261 RingCT/type: yes/0
Extra: 0174cc83b308e81d4be384a717b371ddb8b5dd5ce78d02275a7e0a10fe40b1e65702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f11e519128e8754776f49ec7e3b2ccbb444f8bc21aa259fae0e44489f3ec50 0.600000000000 1401054 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": 942884, "vin": [ { "gen": { "height": 942874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f11e519128e8754776f49ec7e3b2ccbb444f8bc21aa259fae0e44489f3ec50" } } ], "extra": [ 1, 116, 204, 131, 179, 8, 232, 29, 75, 227, 132, 167, 23, 179, 113, 221, 184, 181, 221, 92, 231, 141, 2, 39, 90, 126, 10, 16, 254, 64, 177, 230, 87, 2, 17, 0, 0, 0, 8, 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