Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc89992742070a40658fe5007bafcae9e640e12b14a6567c58f2027619885bc2

Tx prefix hash: 4f97420c0ca5cff5a55eada9412ac0b213b96c2bcb2b67dcb639c363d6c63869
Tx public key: 1b4f415150e900f8824bbb535eedb2ccff45e5ebb7db53e4e0a135c641a8efab
Timestamp: 1581089848 Timestamp [UCT]: 2020-02-07 15:37:28 Age [y:d:h:m:s]: 05:026:12:36:18
Block: 60581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171121 RingCT/type: yes/0
Extra: 011b4f415150e900f8824bbb535eedb2ccff45e5ebb7db53e4e0a135c641a8efab021100000001c71d3ff9000000000000000000

1 output(s) for total of 386.641981803000 dcy

stealth address amount amount idx
00: 2e07bd189405350272aa76b16b3102cc7da8adb35facc897abf1eae2894add0a 386.641981803000 111594 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": 60591, "vin": [ { "gen": { "height": 60581 } } ], "vout": [ { "amount": 386641981803, "target": { "key": "2e07bd189405350272aa76b16b3102cc7da8adb35facc897abf1eae2894add0a" } } ], "extra": [ 1, 27, 79, 65, 81, 80, 233, 0, 248, 130, 75, 187, 83, 94, 237, 178, 204, 255, 69, 229, 235, 183, 219, 83, 228, 224, 161, 53, 198, 65, 168, 239, 171, 2, 17, 0, 0, 0, 1, 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