Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9797f7e40774f151bb9fb15f8f94636115b540c03a4818bb42a42c31f66c8093

Tx prefix hash: ffd6e275e04505c6ccb0bf0eb57200eb87f166bf0d4fe98059314c04b782759f
Tx public key: 9c7ad3b3448263bdf0a4045c254b20a9c96a85bfeca7af7f8f35fac3e3a3962a
Timestamp: 1636361914 Timestamp [UCT]: 2021-11-08 08:58:34 Age [y:d:h:m:s]: 03:127:06:18:38
Block: 369888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869316 RingCT/type: yes/0
Extra: 019c7ad3b3448263bdf0a4045c254b20a9c96a85bfeca7af7f8f35fac3e3a3962a02110000000a42b3953e000000000000000000

1 output(s) for total of 36.509669591000 dcy

stealth address amount amount idx
00: e42c948d2e5a7a8bc0964e0c5ee56611b6ee6e0e7a7d1129577cbd9f39e171a3 36.509669591000 749978 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": 369898, "vin": [ { "gen": { "height": 369888 } } ], "vout": [ { "amount": 36509669591, "target": { "key": "e42c948d2e5a7a8bc0964e0c5ee56611b6ee6e0e7a7d1129577cbd9f39e171a3" } } ], "extra": [ 1, 156, 122, 211, 179, 68, 130, 99, 189, 240, 164, 4, 92, 37, 75, 32, 169, 201, 106, 133, 191, 236, 167, 175, 127, 143, 53, 250, 195, 227, 163, 150, 42, 2, 17, 0, 0, 0, 10, 66, 179, 149, 62, 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