Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b43386007e787b34008f59544a5d6ff88f907c143b7be2d5c1433a31f7c3c6

Tx prefix hash: 50073ef421c470b59694942d79fabfa509ef89309947785d0d5e5ffc8c93cbc0
Tx public key: a55ec0e8c2c17166551f01f93c103d831f7a55ed41242b6a0210b80366174b70
Timestamp: 1702085036 Timestamp [UCT]: 2023-12-09 01:23:56 Age [y:d:h:m:s]: 01:125:01:22:22
Block: 909027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350533 RingCT/type: yes/0
Extra: 01a55ec0e8c2c17166551f01f93c103d831f7a55ed41242b6a0210b80366174b70021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34bc066e7c39d30244157e451380424943fd92e4e45d836fe64dc68deacc27d9 0.600000000000 1366092 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": 909037, "vin": [ { "gen": { "height": 909027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34bc066e7c39d30244157e451380424943fd92e4e45d836fe64dc68deacc27d9" } } ], "extra": [ 1, 165, 94, 192, 232, 194, 193, 113, 102, 85, 31, 1, 249, 60, 16, 61, 131, 31, 122, 85, 237, 65, 36, 43, 106, 2, 16, 184, 3, 102, 23, 75, 112, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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