Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9375a3326d23214a654790f7ffa240439ec789899d75b657658418041332ea5

Tx prefix hash: 06d3cbd9a30bfb0082fee7e59e2e104a0c53d56352e533f086205001ee9c4eb3
Tx public key: 9c481807d42a805dc82e13c902df404d16918cde5b06757167556c3a0d96a983
Timestamp: 1684885985 Timestamp [UCT]: 2023-05-23 23:53:05 Age [y:d:h:m:s]: 02:026:18:53:53
Block: 766695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541132 RingCT/type: yes/0
Extra: 019c481807d42a805dc82e13c902df404d16918cde5b06757167556c3a0d96a98302110000000675e3f0e9000000000000000000

1 output(s) for total of 1.768566415000 dcy

stealth address amount amount idx
00: 4359874b843dd83c3f564be5a6de53f9a72c0b0a0ad1fa8ae7c652dc3deb9776 1.768566415000 1215754 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": 766705, "vin": [ { "gen": { "height": 766695 } } ], "vout": [ { "amount": 1768566415, "target": { "key": "4359874b843dd83c3f564be5a6de53f9a72c0b0a0ad1fa8ae7c652dc3deb9776" } } ], "extra": [ 1, 156, 72, 24, 7, 212, 42, 128, 93, 200, 46, 19, 201, 2, 223, 64, 77, 22, 145, 140, 222, 91, 6, 117, 113, 103, 85, 108, 58, 13, 150, 169, 131, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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