Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddd0c2395ed252e5d1e1811c3ce1ebceebd728ed3d5468ac1503550b4d60409d

Tx prefix hash: 205df506034f826ab9982633f5314a1b4b165573f3430b94412aa785bccbd1d2
Tx public key: 8a4a54c2e5269e7506725018d0b87fcccf91b239abf037f39022b9486dc2a1df
Timestamp: 1706136259 Timestamp [UCT]: 2024-01-24 22:44:19 Age [y:d:h:m:s]: 01:071:07:36:56
Block: 942586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312067 RingCT/type: yes/0
Extra: 018a4a54c2e5269e7506725018d0b87fcccf91b239abf037f39022b9486dc2a1df02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1254146fb2b962737ae39f4cdf4bc050f9ce58509422ded83e94bf0075fe95c 0.600000000000 1400760 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": 942596, "vin": [ { "gen": { "height": 942586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1254146fb2b962737ae39f4cdf4bc050f9ce58509422ded83e94bf0075fe95c" } } ], "extra": [ 1, 138, 74, 84, 194, 229, 38, 158, 117, 6, 114, 80, 24, 208, 184, 127, 204, 207, 145, 178, 57, 171, 240, 55, 243, 144, 34, 185, 72, 109, 194, 161, 223, 2, 17, 0, 0, 0, 4, 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