Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0f6beadf980ae7a576f170d85afa807953536a79f9f7fc18c6c8f1227609024

Tx prefix hash: 609bfa7d843a71da71256e306a8fc0ae969eec287293f5bf605bbd5f3e6c00d9
Tx public key: c664c6ef97be7b62ad26cb3342c45adb8fb0702d9c34b3e70aa8b41568fd5294
Timestamp: 1740167369 Timestamp [UCT]: 2025-02-21 19:49:29 Age [y:d:h:m:s]: 00:228:12:00:33
Block: 1224281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161023 RingCT/type: yes/0
Extra: 01c664c6ef97be7b62ad26cb3342c45adb8fb0702d9c34b3e70aa8b41568fd52940211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd3a4058bdf40ec8a5ac333a8958ad2663e005a79fabc329431cc82148d4677 0.600000000000 1711140 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": 1224291, "vin": [ { "gen": { "height": 1224281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd3a4058bdf40ec8a5ac333a8958ad2663e005a79fabc329431cc82148d4677" } } ], "extra": [ 1, 198, 100, 198, 239, 151, 190, 123, 98, 173, 38, 203, 51, 66, 196, 90, 219, 143, 176, 112, 45, 156, 52, 179, 231, 10, 168, 180, 21, 104, 253, 82, 148, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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