Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0b4569df164b2ba1c3b7cc5dd8cbe9204b79dea80326469abe4bc1354f459c

Tx prefix hash: ac29d7ca4161683f2e824a3c9641c27df26d55af04fc002ae4f00ab8a031c337
Tx public key: 1d2e522ecf3fd57a458c347f350d2fe4b30fe5211190fc58f76688df1c94127f
Timestamp: 1582519223 Timestamp [UCT]: 2020-02-24 04:40:23 Age [y:d:h:m:s]: 04:282:23:07:24
Block: 71491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094664 RingCT/type: yes/0
Extra: 011d2e522ecf3fd57a458c347f350d2fe4b30fe5211190fc58f76688df1c94127f021100000002c71d3ff9000000000000000000

1 output(s) for total of 355.730777171000 dcy

stealth address amount amount idx
00: abb7108834f8e8d2000764dac845d67e875bc762c1bfec743e1ff87485669172 355.730777171000 132018 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": 71501, "vin": [ { "gen": { "height": 71491 } } ], "vout": [ { "amount": 355730777171, "target": { "key": "abb7108834f8e8d2000764dac845d67e875bc762c1bfec743e1ff87485669172" } } ], "extra": [ 1, 29, 46, 82, 46, 207, 63, 213, 122, 69, 140, 52, 127, 53, 13, 47, 228, 179, 15, 229, 33, 17, 144, 252, 88, 247, 102, 136, 223, 28, 148, 18, 127, 2, 17, 0, 0, 0, 2, 199, 29, 63, 249, 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