Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43cc6cbe233bd2ed492318a45ecd60d94e43cce1cbcd99fddb3321c2e6b6ef3a

Tx prefix hash: 9317e0ae4d91fdac64d56f48b3c7269509a2821416fa9946850656d931bcb69c
Tx public key: 6e0bd8bdbeae7e9d782f7ff1b4c4f1a926450284f00321d79e3f2d6167175b49
Timestamp: 1584759833 Timestamp [UCT]: 2020-03-21 03:03:53 Age [y:d:h:m:s]: 04:282:21:18:49
Block: 85916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098719 RingCT/type: yes/0
Extra: 016e0bd8bdbeae7e9d782f7ff1b4c4f1a926450284f00321d79e3f2d6167175b490211000000018c5f723a000000000000000000

1 output(s) for total of 318.658426897000 dcy

stealth address amount amount idx
00: cf0d4146639fd4dfe9cf6e81915897862f7b930b023128916fffccee63b805c0 318.658426897000 155158 of 0

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": 85926, "vin": [ { "gen": { "height": 85916 } } ], "vout": [ { "amount": 318658426897, "target": { "key": "cf0d4146639fd4dfe9cf6e81915897862f7b930b023128916fffccee63b805c0" } } ], "extra": [ 1, 110, 11, 216, 189, 190, 174, 126, 157, 120, 47, 127, 241, 180, 196, 241, 169, 38, 69, 2, 132, 240, 3, 33, 215, 158, 63, 45, 97, 103, 23, 91, 73, 2, 17, 0, 0, 0, 1, 140, 95, 114, 58, 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