Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6614aa3d6509c2f3f2b94efdceb30da28dd71bb679e3cb28027601f4e3be9908

Tx prefix hash: 60c4ad1b87b99af82cb7255b9115b3ec48ea7382762f2b381adbffc0681dd2e1
Tx public key: e54c94598258a9f22c43e9464331c61827cca484d0e5fe870eb5157885d65267
Timestamp: 1659282953 Timestamp [UCT]: 2022-07-31 15:55:53 Age [y:d:h:m:s]: 02:240:11:10:52
Block: 555776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 693058 RingCT/type: yes/0
Extra: 01e54c94598258a9f22c43e9464331c61827cca484d0e5fe870eb5157885d65267021100000008eae24e24000000000000000000

1 output(s) for total of 8.840636259000 dcy

stealth address amount amount idx
00: 0672a2a1585e03c0eb9fb3fcba0bbdccadfb1e463db3fa8d5e1f1b5709e55395 8.840636259000 987692 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": 555786, "vin": [ { "gen": { "height": 555776 } } ], "vout": [ { "amount": 8840636259, "target": { "key": "0672a2a1585e03c0eb9fb3fcba0bbdccadfb1e463db3fa8d5e1f1b5709e55395" } } ], "extra": [ 1, 229, 76, 148, 89, 130, 88, 169, 242, 44, 67, 233, 70, 67, 49, 198, 24, 39, 204, 164, 132, 208, 229, 254, 135, 14, 181, 21, 120, 133, 214, 82, 103, 2, 17, 0, 0, 0, 8, 234, 226, 78, 36, 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