Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82570d33b79a71d89e1ee8737da861341960a274b79044335d645a4f4cbaad91

Tx prefix hash: 1afa26292214c67d45eae8317ad7c1ca980c8b5d79c558e61c022f7362b4e7e2
Tx public key: 526113a7d3827b7e79ee84adc9f1e9318604dcc1b397b106b033b4594a44ac40
Timestamp: 1703280560 Timestamp [UCT]: 2023-12-22 21:29:20 Age [y:d:h:m:s]: 01:327:22:47:34
Block: 918940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493239 RingCT/type: yes/0
Extra: 01526113a7d3827b7e79ee84adc9f1e9318604dcc1b397b106b033b4594a44ac4002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2aa6e73a91750e344df430e8a965c05ea6816ab394617f83e3dc1c64219fb3 0.600000000000 1376604 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": 918950, "vin": [ { "gen": { "height": 918940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2aa6e73a91750e344df430e8a965c05ea6816ab394617f83e3dc1c64219fb3" } } ], "extra": [ 1, 82, 97, 19, 167, 211, 130, 123, 126, 121, 238, 132, 173, 201, 241, 233, 49, 134, 4, 220, 193, 179, 151, 177, 6, 176, 51, 180, 89, 74, 68, 172, 64, 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