Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16ea98cd06d789690c655f375b90f58b76316ffe91119b9f0a9b98aab4705ab

Tx prefix hash: 799ac45cb425fb4a99f9f9a976546c9e3503c092461dac4a57399a9e15192110
Tx public key: 21cb255327f52945c567a0ae258ce5cf8f31626fb1b27a2ce55ba461efef65e7
Timestamp: 1580795351 Timestamp [UCT]: 2020-02-04 05:49:11 Age [y:d:h:m:s]: 06:000:08:23:42
Block: 58445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1410660 RingCT/type: yes/0
Extra: 0121cb255327f52945c567a0ae258ce5cf8f31626fb1b27a2ce55ba461efef65e7021100000003dcee4b4d000000000000000000

1 output(s) for total of 392.959935586000 dcy

stealth address amount amount idx
00: dca6b1d3083f686627bf4e690995a370c3a4cfca7dda88fe74dbdb68a5a376ab 392.959935586000 107959 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": 58455, "vin": [ { "gen": { "height": 58445 } } ], "vout": [ { "amount": 392959935586, "target": { "key": "dca6b1d3083f686627bf4e690995a370c3a4cfca7dda88fe74dbdb68a5a376ab" } } ], "extra": [ 1, 33, 203, 37, 83, 39, 245, 41, 69, 197, 103, 160, 174, 37, 140, 229, 207, 143, 49, 98, 111, 177, 178, 122, 44, 229, 91, 164, 97, 239, 239, 101, 231, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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