Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b218b25d43993a779e906aa3baee718a299b895676635e2cc6a2e5ff821e04d

Tx prefix hash: 2d85271dddc36c26edd77c1d4f81bf24955a06001db3e414778ec7e443b0b356
Tx public key: 57a47ca2fae0b1a89378b5296e9316302408f8cfbab94fb592024fb6a2e0f5f3
Timestamp: 1707046787 Timestamp [UCT]: 2024-02-04 11:39:47 Age [y:d:h:m:s]: 01:110:06:37:10
Block: 950153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339911 RingCT/type: yes/0
Extra: 0157a47ca2fae0b1a89378b5296e9316302408f8cfbab94fb592024fb6a2e0f5f302110000000281d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa47dcc4180ca2c50787b5d0328f5420af623900e7ee6fbb4ac88de452b847dc 0.600000000000 1408721 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": 950163, "vin": [ { "gen": { "height": 950153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa47dcc4180ca2c50787b5d0328f5420af623900e7ee6fbb4ac88de452b847dc" } } ], "extra": [ 1, 87, 164, 124, 162, 250, 224, 177, 168, 147, 120, 181, 41, 110, 147, 22, 48, 36, 8, 248, 207, 186, 185, 79, 181, 146, 2, 79, 182, 162, 224, 245, 243, 2, 17, 0, 0, 0, 2, 129, 215, 29, 85, 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